home *** CD-ROM | disk | FTP | other *** search
- * Dos error data, for use by Guru2.0
- * By E.Lensink
- * CED
- *****************************************
-
- 0103
- @p2
- DOS ERROR:
- @p1
- 103: Not enough memory
- @p2
-
- PROBABLE CAUSE:
- @p1
- You do not have enough free ram to
- carry out the operation.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Close all unneeded windows and stop any
- unneeded tasks, then try again. You may
- need to add more memory to your Amiga.
- \
-
- 0104
- @p2
- DOS ERROR:
- @p1
- 104: Process table full
- @p2
-
- PROBABLE CAUSE:
- @p1
- There is a limit to the number of
- possible processes.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Stop one or more tasks.
- \
-
- 0114
- @p2
- DOS ERROR:
- @p1
- 114: Bad template
- @p2
-
- PROBABLE CAUSE:
- @p1
- Incorrect command line.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0115
- @p2
- DOS ERROR:
- @p1
- 115: Bad number
- @p2
-
- PROBABLE CAUSE:
- @p1
- The program was expecting a numeric
- argument.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0116
- @p2
- DOS ERROR:
- @p1
- 116: Required argument missing
- @p2
-
- PROBABLE CAUSE:
- @p1
- Incorrect command line.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0117
- @p2
- DOS ERROR:
- @p1
- 117: Argument after '=' missing
- @p2
-
- PROBABLE CAUSE:
- @p1
- Incorrect command line.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0118
- @p2
- DOS ERROR:
- @p1
- 118: Too many arguments
- @p2
-
- PROBABLE CAUSE:
- @p1
- Incorrect command line.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0119
- @p2
- DOS ERROR:
- @p1
- 119: Unmatched quotes
- @p2
-
- PROBABLE CAUSE:
- @p1
- Incorrect command line.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0120
- @p2
- DOS ERROR:
- @p1
- 120: Argument line invalid or too long
- @p2
-
- PROBABLE CAUSE:
- @p1
- Your command line is incorrect or
- contains too many arguments.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Consult the program's documentation
- for the correct format.
- \
-
- 0121
- @p2
- DOS ERROR:
- @p1
- 121: File is not executable
- @p2
-
- PROBABLE CAUSE:
- @p1
- You misspelled the command name, or
- the file may not be a loadable
- (program or script) file.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Retype the filename and make sure
- that the file is a program file.
- \
-
- 0122
- @p2
- DOS ERROR:
- @p1
- 122: Invalid resident library
- @p2
-
- PROBABLE CAUSE:
- @p1
- You are trying to use commands with
- a previous version of AmigaDOS; for
- example, Version 2.0 commands with
- Version 1.3 Kickstart.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Use another Kickstart.
- \
-
- 0202
- @p2
- DOS ERROR:
- @p1
- 202: Object is in use
- @p2
-
- PROBABLE CAUSE:
- @p1
- The specified file or directory
- already has a Lock() on it.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Stop the application that is using the
- file or directory, then try again.
- \
-
- 0203
- @p2
- DOS ERROR:
- @p1
- 203: Object already exists
- @p2
-
- PROBABLE CAUSE:
- @p1
- The name that you specified already
- belongs to another file or directory.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Use another name, or delete the
- existing file, then try again.
- \
-
- 0204
- @p2
- DOS ERROR:
- @p1
- 204: Directory not found
- @p2
-
- PROBABLE CAUSE:
- @p1
- AmigaDOS cannot find the directory
- you specified. You may have made
- a typing or spelling error.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Check the directory name and reissue
- the command.
- \
-
- 0205
- @p2
- DOS ERROR:
- @p1
- 205: Object not found
-
- @p2
- PROBABLE CAUSE:
- @p1
- AmigaDOS cannot find the file or
- device you specified. You may have
- made a typing or spelling error.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Check the filename or the device
- name and reissue the command.
- \
-
- 0206
- @p2
- DOS ERROR:
- @p1
- 206: Invalid window description
- @p2
-
- PROBABLE CAUSE:
- @p1
- This error occurs when specifying a
- window size for the Output Window
- You may have made the window too big
- or too small, or ommitted an argument.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Reissue the window specification.
- \
-
- 0209
- @p2
- DOS ERROR:
- @p1
- 209: Packet request type unknown
- @p2
-
- PROBABLE CAUSE:
- @p1
- You have asked a device handler
- to attempt an operation it cannot do.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Check the request code passed to
- device handlers for the appropriate
- response.
- \
-
- 0210
- @p2
- DOS ERROR:
- @p1
- 210: Object name invalid
- @p2
-
- PROBABLE CAUSE:
- @p1
- There is an invalid character in the
- filename or the filename is too long.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Retype the name, being sure not to
- use any invalid characters, or
- exceed the maximum length.
- \
-
- 0211
- @p2
- DOS ERROR:
- @p1
- 211: Invalid object lock
- @p2
-
- PROBABLE CAUSE:
- @p1
- You have used something that is not
- a valid lock.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Check that your code only passes valid
- locks to AmigaDOS calls that expect
- locks.
- \
-
- 0212
- @p2
- DOS ERROR:
- @p1
- 212: Object not of required type
- @p2
-
- PROBABLE CAUSE:
- @p1
- You may have specified a filename for
- an operation that requires a
- directory name, or vice versa.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Consult the documentation for the
- correct command format.
- \
-
- 0213
- @p2
- DOS ERROR:
- @p1
- 213: Disk not validated
- @p2
-
- PROBABLE CAUSE:
- @p1
- The disk is corrupt.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- If you've just inserted the disk, wait
- for the validation process to finish.
- If that doesn't work you may have to
- use DISKDOCTOR.
- \
-
- 0214
- @p2
- DOS ERROR:
- @p1
- 214: Disk is write-protected
- @p2
-
- PROBABLE CAUSE:
- @p1
- The plastic tab is in the
- write-protect position.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- If you're certain you want to write to
- that particular disk, deprotect it.
- Otherwise, use a different disk.
- \
-
- 0215
- @p2
- DOS ERROR:
- @p1
- 215: Rename across devices attempted
- @p2
-
- PROBABLE CAUSE:
- @p1
- RENAME only changes a filename on the
- same volume.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Use the MOVE command instead. (PD)
- \
-
- 0216
- @p2
- DOS ERROR:
- @p1
- 216: Directory not empty
- @p2
-
- PROBABLE CAUSE:
- @p1
- This error occurs if you attempt to
- delete a directory that contains
- files or subdirectories.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Use the ALL option of DELETE.
- \
-
- 0217
- @p2
- DOS ERROR:
- @p1
- 217: Too many levels
- @p2
-
- PROBABLE CAUSE:
- @p1
- You've exceeded the limit of 15 soft
- links.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Reduce the number of soft links.
- \
-
- 0218
- @p2
- DOS ERROR:
- @p1
- 218: Device (or volume) not mounted
- @p2
-
- PROBABLE CAUSE:
- @p1
- the device has not been mounted with
- the MOUNT command.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Insert the correct disk, check the
- spelling of the device name, mount the
- device, or revise your MountList file.
- \
-
- 0219
- @p2
- DOS ERROR:
- @p1
- 219: Seek error
- @p2
-
- PROBABLE CAUSE:
- @p1
- You have attempted to call SEEK with
- invalid arguments.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Make sure that you only SEEK within
- the file. You cannot SEEK outside the
- bounds of the file.
- \
-
- 0220
- @p2
- DOS ERROR:
- @p1
- 220: Comment is too long
- @p2
-
- PROBABLE CAUSE:
- @p1
- Your filenote has exceeded the maximum
- number of chatacters (79).
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Use a shorter comment.
- \
-
- 0221
- @p2
- DOS ERROR:
- @p1
- 221: Disk is full
-
- @p2
- PROBABLE CAUSE:
- @p1
- There is not enough room on the disk
- to perform the requested operation.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Delete some unnecessary files or
- directories, or use a different disk.
- \
-
- 0222
- @p2
- DOS ERROR:
- @p1
- 222: Object is protected from deletion
-
- @p2
- PROBABLE CAUSE:
- @p1
- The d (deletable) protection bit of
- the file or directory is clear.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- If you are certain that you want to
- delete the file or directory, use
- PROTECT to set the d bit.
- \
-
- 0223
- @p2
- DOS ERROR:
- @p1
- 223: File is write protected
-
- @p2
- PROBABLE CAUSE:
- @p1
- The w (writeable) protection bit of
- the file is clear.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- If you are certain that you want to
- overwrite the file, use PROTECT to
- set the w bit.
- \
-
- 0224
- @p2
- DOS ERROR:
- @p1
- 224: File is read protected
- @p2
-
- PROBABLE CAUSE:
- @p1
- The r (readable) protection bit of
- the file is clear.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Use PROTECT to set the r bit of the
- file.
- \
-
- 0225
- @p2
- DOS ERROR:
- @p1
- 225: Not a valid DOS disk
-
- @p2
- PROBABLE CAUSE:
- @p1
- The disk in the drive is not an
- AmigaDOS disk, it has not been
- formatted, or it is corrupt.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- If the disk has not been formatted,
- use FORMAT to do so.
- \
-
- 0226
- @p2
- DOS ERROR:
- @p1
- 226: No disk in drive
- @p2
-
- PROBABLE CAUSE:
- @p1
- The disk is not properly inserted
- in the specified drive.
-
- @p2
- RECOVERY SUGGESTION:
- @p1
- Insert the appropriate disk in the
- specified drive.
- \
-
- 0232
- @p2
- DOS ERROR:
- @p1
- 232: No more entries in directory
-
- @p2
- PROBABLE CAUSE:
- @p1
- This indicates that the AmigaDOS call
- EXNEXT has no more entries in the
- directory you are examining.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- Stop calling EXNEXT.
- \
-
- 0233
- @p2
- DOS ERROR:
- @p1
- 233: Object is soft link
- @p2
-
- PROBABLE CAUSE:
- @p1
- You tried to perform an operation on a
- soft link that should only be
- performed on a file or directory.
- @p2
-
- RECOVERY SUGGESTION:
- @p1
- AmigaDOS retries the operation.
- \
-
-
-